.aiox-core/workflow-intelligence/__tests__/integration.test.js (1)

8-8: 💤 Low value

Relative import violates coding guidelines.

Line 8 uses a relative import path ('../index'). As per coding guidelines, absolute imports should be used instead of relative imports in all code.

Consider refactoring to absolute import

-const wis = require('../index');
+const wis = require('.aiox-core/workflow-intelligence/index');

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.aiox-core/workflow-intelligence/__tests__/integration.test.js at line 8,
Replace the relative require('../index') in the test (the line that assigns to
variable wis) with an absolute module import of the workflow-intelligence
package/module (use the package name or its published path instead of ../index),
update any package.json exports if necessary so the absolute import resolves,
and run the tests to confirm the change.

.aiox-core/workflow-intelligence/__tests__/workflow-registry.test.js (1)

9-13: 💤 Low value

Relative import violates coding guidelines.

The require statement on line 13 uses a relative path ('../registry/workflow-registry'). As per coding guidelines, absolute imports should be used instead of relative imports in all code.

While relative imports are common in test files, the guideline applies to **/*.{js,jsx,ts,tsx} without exceptions.

Consider refactoring to absolute import

-const {
-  WorkflowRegistry,
-  createWorkflowRegistry,
-  DEFAULT_CACHE_TTL,
-} = require('../registry/workflow-registry');
+const {
+  WorkflowRegistry,
+  createWorkflowRegistry,
+  DEFAULT_CACHE_TTL,
+} = require('.aiox-core/workflow-intelligence/registry/workflow-registry');

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.aiox-core/workflow-intelligence/__tests__/workflow-registry.test.js around
lines 9 - 13, The test uses a relative require for the exports WorkflowRegistry,
createWorkflowRegistry, and DEFAULT_CACHE_TTL; replace the relative import
('../registry/workflow-registry') with the project's absolute module import (use
the repository/module root alias) so the test requires the module via its
absolute path (importing WorkflowRegistry, createWorkflowRegistry,
DEFAULT_CACHE_TTL) rather than a relative ../ path to comply with the coding
guideline.

tests/core/workflow-navigator-integration.test.js (1)

22-76: 💤 Low value

Multiple relative imports in jest.mock() calls violate coding guidelines.

Lines 22-76 contain numerous jest.mock() calls with relative paths (e.g., '../../.aiox-core/core/session/context-detector'). As per coding guidelines, absolute imports should be used instead of relative imports in all code.

Note: In Jest test files, relative paths in jest.mock() are standard practice for mocking adjacent modules.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@tests/core/workflow-navigator-integration.test.js` around lines 22 - 76,
Replace the relative module paths used in the jest.mock() calls with the
project's approved absolute import aliases so the mocks follow coding
guidelines; update each mocked module reference (context-detector,
git-config-detector, project-status-loader, config-resolver,
greeting-preference-manager, permissions, session-state, surface-checker) to use
the configured absolute import (e.g., the project's module alias or package
name) in the jest.mock(...) calls and keep the mock implementations unchanged
(ensure names like loadProjectStatus, resolveConfig, PermissionMode,
SessionState, SurfaceChecker remain targeted the same way).